Computer system, server module, and storage module

ABSTRACT

An exemplary computer system includes a server module including a first processor and first memory, a storage module including a second processor, a second memory and a storage device, and a transfer module. The transfer module retrieves a first transfer list including an address of a first storage area, which is set on the first memory for a read command, from the server module. The transfer module retrieves a second transfer list including an address of a second storage area in the second memory, in which data corresponding to the read command read from the storage device is stored temporarily, from the storage module. The transfer module sends the data corresponding to the read command in the second storage area to the first storage area by controlling the data transfer between the second storage area and the first storage area based on the first and second transfer lists.

CLAIM OF PRIORITY

The present application claims priority from Japanese patent applicationJP2013-101842 filed on May 14, 2013, the content of which is herebyincorporated by reference into this application.

BACKGROUND

This invention relates to a computer system, a server module, and astorage module for performing high-speed data transfer between theserver module and the storage module.

Computer systems in which a server is connected with a storage apparatusto be accessed by the server include the following known systems.

One of such known computer systems is a computer system in which aserver is connected with a storage apparatus via a network such as a SAN(for example, refer to JP 2012-118973 A).

JP 2012-118973 A discloses a storage appliance system comprising atleast one application server for locally executing an application andone or more storage servers in communication with said at least oneapplication server for I/O transmission therebetween.

This computer system is to be used for a large-scale computer system.This computer system has an advantage of high flexibility in systemconfiguration but has a disadvantage of high cost for installing andoperating apparatuses forming a network such as a SAN.

Another known computer system is a computer system in which multipleservers are connected with a storage apparatus via a disk interface (forexample, refer to JP 2006-309477 A).

JP 2006-309477 A discloses a system of a blade server apparatuscomprising one or more server modules, one or more storage modules, anda management module for managing the whole apparatus, which areinstalled in slots to form the blade server apparatus using a backplanefor enabling signal transmission among the modules, wherein the servermodules and the storage modules are interconnected via a disk interfaceon the backplane; each server module and storage module has a modulemanagement unit for controlling the power in the module; and the modulemanagement unit controls the power in the server module or the storagemodule according to a power control signal sent from the managementmodule.

This computer system is to be used for a small-scale computer system.This computer system can provide dense servers but has a problem of lowsystem flexibility.

In recent years, computer systems that include servers and a storageapparatus within a chassis are increasingly employed. Such a computersystem can show flexible and excellent performance at a low cost. Theservers and the storage apparatus are connected to one another via abackplane within the same chassis.

SUMMARY

The servers and the storage apparatus can communicate at high speedbecause of the connection via the backplane. However, the formats ofcommands handled by the servers and the storage apparatus are differentand moreover, the formats of data are different. Accordingly, theservers and the storage apparatus need to convert the command format andthe data format.

Since this conversion generates overhead in the servers and the storageapparatus, it is difficult to attain high-speed data transfer or toincrease the throughput to the performance limit.

Furthermore, existing technology does not provide a module that enableshigh-speed data transfer between the memory of a server and the memoryof a storage apparatus.

The invention has been accomplished in view of the foregoing problems.In other words, an object of this invention is to achieve high-speeddata transfer between a server and a storage apparatus.

An aspect of the invention is a computer system including a servermodule including a first processor and first memory, a storage moduleincluding a second processor, a second memory and a storage device, anda transfer module being coupled to the server module and the storagemodule, controlling a data transfer between the server module and thestorage module. When the first processor of the server issues a readcommand to the second processor of the storage module via the transfermodule, the transfer module retrieves a first transfer list including anaddress of a first storage area, which is set on the first memory by thefirst processor for the read command, from the server module. Thetransfer module further retrieves a second transfer list including anaddress of a second storage area in the second memory, in which datacorresponding to the read command read from the storage device is storedtemporarily by the second processor, from the storage module. Thetransfer module sends the data corresponding to the read command in thesecond storage area to the first storage area by controlling the datatransfer between the second storage area and the first storage areabased on the first transfer list and the second transfer list. Thetransfer module sends a notice of a completion of the data transfer tothe second processor. The second processor is configured to send anotice of a completion of the read command in response to receiving thenotice of the completion of the data transfer.

The invention provides a transfer module for performing high-speed datatransfer via neither the processor of a server module nor the processorof a storage module.

Problems, configurations, and effects of this invention other than thosedescribed above are clarified through the description of embodimentshereinafter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a configuration example of acomputer system in Embodiment 1 of this invention;

FIG. 2 is a block diagram illustrating a software configuration of aserver module in Embodiment 1 of this invention;

FIG. 3 is a block diagram illustrating a software configuration of astorage module in Embodiment 1 of this invention;

FIG. 4 is a block diagram illustrating a configuration example of atransfer module in Embodiment 1 of this invention;

FIG. 5 is a sequence diagram illustrating an example of data transfer inEmbodiment 1 of this invention;

FIG. 6 is a sequence diagram illustrating an example of data transfer inEmbodiment 1 of this invention;

FIG. 7 is a block diagram illustrating a configuration example of acomputer system in Embodiment 2 of this invention;

FIG. 8 is a block diagram illustrating a configuration example of acomputer system in Embodiment 3 of this invention;

FIG. 9 illustrates an example in which the transfer module controlstransfer of 8192 bytes data to be read for a read request from thememory of the storage module to the memory of the server module inEmbodiment 1 of this invention; and

FIG. 10 illustrates an example in which the transfer module controlstransfer of 8192 bytes data to be written for a write request from thememory of the server module to the memory of the storage module inEmbodiment 1 of this invention.

DETAILED DESCRIPTION OF THE EMBODIMENTS

Hereinafter, embodiments of this invention are described in detail withreference to the accompanying drawings.

Embodiment 1

FIG. 1 is a block diagram illustrating a configuration example of acomputer system in Embodiment 1 of this invention.

The computer system in Embodiment 1 is composed of a server apparatus100, server modules 200, and storage modules 300.

The server apparatus 100 includes a plurality of server modules 200, astorage module 300, and a backplane 400. In the example shown in FIG. 1,the server apparatus 100 includes a server module 200-1, a server module200-2, and a storage module 300-1.

The server modules 200 are computers for executing predeterminedservice. The storage module 300 is a computer for storing data to beused by the server modules 200. In this embodiment, the storage module300 provides LUs (Logical Units) to the server modules 200.

Each server module 200 includes a processor 210, a memory 220, atransfer module 230, an HBA 240, a NIC 250, and an I/F 260. Thecomponents of the server module 200 are connected with one another viaan I/O bus. The I/O bus includes the PCI bus, the PCIe bus, the systembus, and the like. This invention is not limited to the type of the I/Obus connecting the components.

The processor 210 executes programs stored in the memory 220. Theprocessor 210 executes a program stored in the memory 220 to perform afunction of the server module 200.

The memory 220 stores programs to be executed by the processor 210 andinformation required to execute the programs. The programs andinformation to be stored in the memory 220 will be described later withFIG. 2.

The programs and information to be stored in the memory 220 may bestored in an LU provided by the storage module 300 or other area. Inthis case, the processor 210 acquires a program and information from thestorage area of the LU or other area holding the program to load theacquired program and information to the memory 220.

The transfer module 230 controls data transfer between the server module200 and the storage module 300. The detailed configuration of thetransfer module 230 will be described later with FIG. 4.

The HBA 240 is an interface for connecting the server module 200 to anexternal apparatus via a network such as a SAN (Storage Area Network).The NIC 250 is an interface for connecting the server module 200 to anexternal apparatus via a network such as a LAN (Local Area Network). TheI/F 260 is a connector for connecting the server module 200 to thebackplane 400.

The transfer module 230 may be mounted on a board of the server module200 as a chip (LSI) or mounted on an adapter such as the HBA or NIC.However, this invention is not limited to the way to mount the transfermodule 230.

Each storage module 300 includes disk controllers 310, a TBA (Target BusAdapter) 350, I/Fs 360, and storage devices 370. The components includedin the storage module 300 are connected with one another via an I/O bus.The I/O bus includes the PCI bus, the PCIe bus, the SAS (Serial AttachedSCSI) interface, the system bus, and the like. However, this inventionis not limited to the type of I/O bus connecting the components.

The disk controllers 310 manage storage areas and control associationrelations between the server modules 200 and the storage areas. Eachdisk controller 310 includes a processor 320 and a memory 330.

In this embodiment, the storage module 300-1 has two disk controllers: adisk controller 310-1 and a disk controller 310-2. This is because theredundant disk controllers enhance the fault tolerance.

The disk controller 310-1 is connected to the I/F 360-1 and the diskcontroller 310-2 is connected to the I/F 360-2. The disk controllers310-1 and 310-2 are each connected to the TBA 350 and the storagedevices 370.

The processor 320 executes programs stored in the memory 330. Theprocessor 320 executes a program held in the memory 330 to perform afunction of the storage module 300.

The memory 330 stores programs to be executed by the processor 320 andinformation required to execute the programs. The programs andinformation to be stored in the memory 330 will be described later withFIG. 3.

The programs and information to be stored in the memory 330 may bestored in a storage device 370 or other area. In this case, theprocessor 320 acquires a program and information from the storage device370 or other area to load the acquired program and information to thememory 330.

The TBA 350 is an interface for connecting the storage module 300 to anexternal apparatus via a network such as a SAN. The I/Fs 360 areconnectors for connecting the storage module 300 to the backplane 400.

Each storage device 370 is a device for storing data, which may be anHDD (Hard Disk Drive), an SSD (Solid State Drive), or the like.

In this embodiment, the storage module 300 configures a RAID using aplurality of storage devices and creates LUs from a RAID volume toprovide the LUs to the server modules 200. Each LU stores programs suchas an OS 221 (refer to FIG. 2) and an application 223 (refer to FIG. 2)and information required to execute the programs.

The backplane 400 connects the server modules 200 with the storagemodule 300. The backplane 400 has a plurality of I/Fs 410 for connectingthe server modules 200 with the storage module 300. The backplane 400also has an I/O bus for connecting the I/Fs 410.

Now, connections in the computer system are described.

The server module 200-1 and the backplane 400 in the server apparatus100 are connected via two connection lines. The server module 200-1 isconnected to the I/F 360-1 and the I/F 360-2 in the storage module 300via these two connection lines.

The I/Fs 360 in the storage module 300 are configured to be connected todifferent disk controllers 310; the I/F 360-1 is connected to the diskcontroller 310-1 and the I/F 360-2 is connected to the disk controller310-2. Accordingly, the server module 200-1 is connected to the two diskcontrollers 310-1 and 310-2 one to one.

In this embodiment, both of the two disk controllers 310-1 and 310-2 areactive. Accordingly, the two disk controllers 310-1 and 310-2independently perform I/O processing to raise the throughput. In themeanwhile, if a fault occurs in the disk controller 310-1, the diskcontroller 310-2 can continue the I/O processing. Consequently, theservice can be kept being executed.

The server modules 200-1 and 200-2 in the server apparatus 100 areconnected to an external server module 200-3 via a LAN 600 and connectedto an external storage module 300-2 via a SAN 500.

The storage module 300-1 in the server apparatus 100 is connected to theexternal server modules 300-2 via the SAN 500.

FIG. 2 is a block diagram illustrating a software configuration of theserver module 200 in Embodiment 1 of this invention.

The memory 220 stores programs to implement the OS 221 and anapplication 223. The memory 220 also stores a transfer list 224.

The OS 221 manages the server module 200. The OS 221 includes a storageaccess unit 222 for controlling accesses between the server module 200and the storage module 300. The storage access unit 222 may beimplemented using a device driver for operating the transfer module 230.

The OS 221 has functions including a not-shown file system but they areomitted since they are known in the art.

The application 223 executes predetermined service. This invention isnot limited to the kind of the application.

The transfer list 224 is information to be used in data transfer betweenthe memory 220 of the server module 200 and the memory 330 of thestorage module 300 not via the processor 210. This embodiment employs anSGL (Scatter Gather List) used in DMA transfer as the transfer list 224.

The SGL includes addresses and address lengths. An address is a startaddress of a storage area in the memory 220 to store designated data. Anaddress length is a value representing the address range correspondingto the storage area in the memory 220.

The transfer list 224 is information to be held in data transfer on atemporal basis.

FIG. 3 is a block diagram illustrating a software configuration of thestorage module 300 in Embodiment 1 of this invention.

FIG. 3 illustrates the memory 330 in the disk controller 310-1 by way ofexample. The memory 330 in the disk controller 310-2 has the samesoftware configuration.

The memory 330 stores a program for implementing a storage controller331. The memory 330 also stores the transfer list 334.

The storage controller 331 controls I/O processing between the servermodules 200 and the storage module 300. The storage controller 331includes an I/O processing unit 332 and a storage device controller 333.

The I/O processing unit 332 receives I/O requests from the servermodules 200 and controls read processing or write processing based onthe I/O request. The storage device controller 333 controls writing toand reading from the storage devices 370.

The I/O processing unit 332 can be implemented by a device driver foroperating the transfer module 230. The storage device controller 333 canbe implemented by a device driver for operating the storage devices 370.

The transfer list 334 is information to be used in data transfer betweenthe memory 220 of a server module 200 and the memory 330 of the storagemodule 300 not via the processor 320. In this embodiment, an SGL used inDMA transfer is used as the transfer list 334.

The transfer list 334 is information stored in data transfer on atemporal basis.

FIG. 4 is a block diagram illustrating a configuration example of thetransfer module 230 in Embodiment 1 of this invention.

The transfer module 230 includes a data transfer unit 231, a protocolengine 234, a bridge 235, and a plurality of connection ports 236.

The data transfer unit 231 controls data transfer between the memory 220of the server module 200 and the memory 330 of the storage module 300.The data transfer unit 231 in this embodiment includes a DMA controller232 and a data checker 233.

The DMA controller 232 controls DMA transfer between the memory 220 ofthe server module 200 and a memory 330 of the storage module 300. Thedata checker 233 attaches and removes data assurance codes. The datachecker 233 also checks integrity of data based on the assurance codes.As the data assurance code, DIF (Data Integrity Field) may be used.

In a common computer system, the server module handles 512-byte data andthe storage module handles 520-byte data, which is generated byattaching a data assurance code to the 512-byte data. It is assumed thatthe data handled by the server module 200 and the data handled by thestorage module 300 in this embodiment are the same as those in thecommon computer system.

The protocol engine 234 converts a command used by the server module 200to and from a command used by the storage module 300.

The bridge 235 controls communication between devices connected via theconnection ports. For example, the bridge 235 converts a signal into asignal different in the number of lanes. The bridge 235 is used when theaforementioned DMA transfer is unnecessary.

The connection ports 236 are ports for connecting to other devices. Inthis embodiment, the connection port 236-1 is connected to the processor210; the connection ports 236-2 and 236-3 are connected to the I/F 260.For example, in the case where the I/O bus connecting the devices is aPCIe bus, PCIe ports are used as the connection ports 236.

FIGS. 5 and 6 are sequence diagrams illustrating examples of datatransfer in Embodiment 1 of this invention.

FIG. 5 illustrates a processing flow of reading performed when theserver module 200 retrieves data from the storage module 300. FIG. 6illustrates a processing flow of writing performed when the servermodule 200 writes data to the storage module 300. The followingdescription explains the case where an I/O request is issued to the diskcontroller 310-1 of the storage module 300 by way of example.

First, reading data is explained.

When the OS 221 receives a request to read data stored in the storagemodule 300 from the application 223, it invokes the storage access unit222.

The storage access unit 222 prepares a buffer for temporarily storingthe data to be read in the memory 220 (Step S101). The storage accessunit 222 creates a transfer list 224 and writes the created transferlist 224 to the memory 220 (Step S102). The transfer list 224 includesthe addresses, the address lengths, and other information to store thedata retrieved from the storage module 300 to the buffer.

The storage access unit 222 further sends a read request to the storagecontroller 331 of the disk controller 310-1 (Step S103). This readrequest is a command used in the server module 200. Accordingly, thiscommand is in a format different from the one used in the storage module300. In other words, the server module 200 and the storage module 300use different protocols.

In the following description, the command used by the server module 200is referred to as server command and the command used by the storagemodule 300 is referred to as storage command.

When the transfer module 230 receives a read request (server command)from the storage access unit 222, it converts the read request to astorage command to send the converted read request (storage command) tothe storage controller 331 (Step S104). Specifically, the followingprocessing is performed.

The data transfer unit 231 analyzes the received read request (servercommand). Since the received read request (server command) is a servercommand to be sent to the storage module 300, the data transfer unit 231instructs the protocol engine 234 to convert the command.

The protocol engine 234 converts the received read request (servercommand) from the server command to the storage command and outputs theconverted read request (storage command) to the data transfer unit 231.

The data transfer unit 231 sends the input read request (storagecommand) to the storage controller 331 of the storage module 300.

Described above is the explanation of the processing at Step S104.

Upon receipt of the read request (storage command), the storagecontroller 331 retrieves the data to be read from the storage device 370and copies the retrieved data to the memory 330 (Step S105).Specifically, the following processing is performed.

The I/O processing unit 332 issues a read request for the storage device370 based on the read request (storage command) and invokes the storagedevice controller 333.

The invoked storage device controller 333 retrieves the designated datafrom the storage device 370 in accordance with the issued read requestto output the data to the I/O processing unit 332.

The I/O processing unit 332 copies the input data to the memory 330.

Since the read request (storage command) has already been converted to astorage command by the transfer module 230 in this embodiment, the I/Oprocessing unit 332 does not have to convert the command.

Described above is the explanation of the processing at Step S105.

The storage controller 331 creates a transfer list 334 and writes thecreated transfer list 334 to the memory 330 (Step S106). The transferlist 334 includes the addresses, the address lengths, and otherinformation to retrieve the data copied to the memory 330.

Next, the storage controller 331 sends a DMA transfer request to thetransfer module 230 (Step S107).

Upon receipt of the DMA transfer request, the transfer module 230retrieves the transfer list 224 from the memory 220 of the server module200 (Step S108) and retrieves the transfer list 334 from the memory 330of the storage module 300 (Step S109).

Specifically, the DMA controller 232 in the data transfer unit 231acquires the address to access the transfer list 224 held in the memory220 of the server module 200 and the address to access the transfer list334 held in the memory 330 of the storage module 300. It should be notedthat the DMA controller 232 may acquire the transfer lists 224 and 334themselves. The DMA controller 232 temporarily holds the acquiredaddresses or the transfer lists 224 and 334.

In the following description, the address to access the transfer list224 held in the memory 220 of the server module 200 may be referred toas first address and the address to access the transfer list 334 held inthe memory 330 of the storage module 300 may be referred to as secondaddress.

The transfer module 230 refers to the transfer list 334 held in thememory 330 of the storage module 300 to retrieve the data copied to thememory 330 (Step S110).

Specifically, the DMA controller 232 in the data transfer unit 231refers to the transfer list 334 held in the memory 330 of the storagemodule 300 with the second address to retrieve the data copied to thememory 330. The DMA controller 232 is to retrieve data on apredetermined data size basis. For example, the DMA controller 232retrieves data in blocks of 520 bytes.

Next, the transfer module 230 writes the retrieved data to the memory220 of the server module 200 (Step S111). Specifically, the followingprocessing is performed.

The data checker 233 in the data transfer unit 231 converts theretrieved data into the data format for the server module 200. Forexample, the data checker 233 removes the data assurance code attachedto the retrieved data. Through this operation, the data is convertedinto 512-byte data to be handled by the server module 200.

The data transfer unit 231 refers to the transfer list 224 held in thememory 220 of the server module 200 with the first address and refers tothe transfer list 334 held in the memory 330 of the storage module 300with the second address.

The data transfer unit 231 determines the storage area of the memory 220to write the converted data based on the transfer lists 224 and 334.Then, the DMA controller 232 in the data transfer unit 231 writes theconverted data to the determined storage area in the memory 220.

For example, to determine the storage area in the memory 220, the datatransfer unit 231 adjusts the alignment. This is because the address ofthe storage area should be adjusted between the memories 220 and 330 inview of the difference in address length of data handled between theserver module 200 and the storage module 300.

The data transfer unit 231 repeats the foregoing processing until allthe data to be read has been retrieved.

The data transfer unit 231 may check the integrity of the retrieved databased on the data assurance code. Upon detection of some error in theretrieved data, the data transfer unit 231 may retrieve the data fromthe memory 330 of the storage module 300 again or notify the storagecontroller 331 of the detection of data error.

Described above is the explanation of the processing of Step S111.

Next, after writing all the data to be read to the memory 220, thetransfer module 230 sends a notice of completion of DMA transfer to thestorage controller 331 (Step S112).

Upon receipt of the notice of completion of DMA transfer, the storagecontroller 331 sends a notice of completion (storage command) for the OS221 (Step S113).

Upon receipt of the notice of completion (storage command), the transfermodule 230 converts the notice of completion (storage command) from thestorage command to the server command and sends the converted notice ofcompletion (server command) to the OS 221 (Step S114). Since theconversion of the command is similar to Step S104, the explanation isomitted.

In the case where the transfer lists 224 and 334 themselves areretrieved at Steps S108 and S109, the transfer module 230 refers to thetransfer lists 224 and 334 and adjusts the alignment to create aconversion list for data storage. In this case, the data transfer unit231 determines the storage area of the memory 220 to write the converteddata based on the conversion list. The DMA controller 232 then writesthe converted data to the determined storage area in the memory 220.

For example, the conversion list could be a list which associates theaddresses in the transfer list 224 with the addresses in the transferlist 334.

The creation of the conversion list, as described above, needs to takethe alignment into account. This is because the data unit size handledby the server module 200 is different from the data unit size handled bythe storage module 300. Further, other causes are the effects from thedeletion of the assurance codes by the data checker 233, the virtualstorage management by the OS 221 acting in the server module 200 and thememory management by the storage controller 331 acting in the storagemodule 300.

For example, when reading 8192 bytes data from the server module 300,assurance codes are attached to the data and the data size is 8320 bytesin the storage module 300. The DMA transfer on the PCIe bus transfersdata in power-of-two bytes blocks. Thus, the conversion list is createdso as to carry out transfers two times for 8192 bytes data and 128 bytesdata.

On the other hand, when the transfer list in the server module 200designates noncontiguous two 4096 bytes areas for reading 8192 bytes,the conversion list is created so as to carry out transfers four timesfor 4096 bytes data, 64 bytes data, 4096 bytes data, 64 bytes data.

Referring to FIG. 9, an example case will be described in which thetransfer module 230 controls transfer of 8192 bytes data to be read fora read request from the memory 330 of the storage module 300 to thememory 220 of the server module 200.

The transfer module 230 acquires the transfer list 224 from the servermodule 200. As described above, the transfer list 224 indicates thestart address and the data length of each of areas prepared on thememory 220 by the server module 200 for storing temporarily data to beread for a read request. The transfer list 224 in FIG. 9 indicates thatthe 4096 bytes area starting from the address A and the 4096 bytes areastarting from the address B are prepared on the memory 220 for storingtemporarily 8192 bytes read data. The transfer module 230 acquires thetransfer list 334 from the storage module 300. As described above, thestorage module 300 copies (stores temporarily) data to be read inaccordance with a read request from the storage device 370 to the memory330 along with the corresponding assurance codes at Step S105. Thetransfer list 334 indicates the start address and the address length ofeach of areas prepared on the memory 330 of the storage module 300 andstoring temporarily data to be read for a read request. The transferlist 334 in FIG. 9 indicates that the 8192 bytes read data for the readrequest and the assurance codes are stored in the 8320 bytes areastarting from the address A′.

The transfer module 230 creates a conversion list based on the transferlist 224 and the transfer list 334. Specifically, the transfer module230 identifies the addresses of the areas storing the assurance codesfrom the transfer list 334. The transfer module 230 associates theaddresses of areas excluding the areas storing the assurance codes(namely, areas storing the read data for the read request on the memory330) as the data transfer source addresses with the addresses on thememory 220 of the server module 200 designated for storing temporarilythe read data in the transfer list 224 as the data transfer destinationaddresses. The conversion list in FIG. 9 associates the address of the4096 bytes area starting from the address A′ on the memory 330 as thedata transfer source address with the 4096 bytes area starting from theaddress A on the memory 220 as the data transfer destination address.Further, the conversion list in FIG. 9 associates the address of the4096 bytes area starting from the address A′+4160 bytes on the memory330 as the data transfer source address with the 4096 bytes areastarting from the address B on the memory 220 as the data transferdestination address.

The transfer module 230 controls the transfer of the data to be read forthe read request from the memory 330 of the storage module 300 to thememory 220 of the server module 200 based on the created conversionlist.

As described above, the conversion list allows the transfer module 230to manage integrally the memory 220 and the memory 330. Therefore, thetransfer module 230 is capable of controlling directly the data transferbetween the memory 220 and the memory 330 without other processors. Asthe transfer module 230 controls directly the data transfer between thememory 220 and the memory 330 in this example, the overhead is inhibitedand the high-speed data transfer between the memory 220 and the memory330 is achieved in comparison with data transfer through pluralprocessors (for example, the processor 320 of the storage module 300 andthe processor 220 of the server module 200) or buffer memories of theprocessors in the data transfer.

Next, writing data is described.

When the OS 221 receives a request to write data to the storage module300 from the application 223, it invokes the storage access unit 222.

The storage access unit 222 copies the data to be written to the memory220 (Step S201). The storage access unit 222 creates a transfer list 224and writes the created transfer list 224 to the memory 220 (Step S202).The transfer list 224 includes the addresses, the address lengths, andother information to retrieve the data copied to the memory 220.

The storage access unit 222 sends a write request (server command) forthe storage controller 331 (Step S203).

When the transfer module 230 receives the write request (servercommand), it converts the write request (server command) from the servercommand into the storage command and sends the converted write request(storage command) to the storage controller 331 (Step S204).Specifically, the following processing is performed.

The data transfer unit 231 analyzes the received write request (servercommand). Since the received write request (server command) is a servercommand to be sent to the storage module 300, the data transfer unit 231instructs the protocol engine 234 to convert the command.

The protocol engine 234 converts the received write request (servercommand) from the server command to the storage command and outputs theconverted write request (storage command) to the data transfer unit 231.

The data transfer unit 231 sends the input write request (storagecommand) to the storage controller 331 of the storage module 300.

Described above is the explanation of the processing at Step S204.

Upon receipt of the write request (storage command), the storagecontroller 331 prepares a buffer for temporarily storing the data to bewritten (Step S205). The storage controller 331 further creates atransfer list 334 and writes the created transfer list 334 to the memory330 (Step S206). The transfer list 334 includes the addresses, theaddress lengths, and other information to store the data to be writtento the buffer.

Next, the storage controller 331 sends a DMA transfer request to thetransfer module 230 (Step S207).

Upon receipt of the DMA transfer request, the transfer module 230retrieves the transfer list 224 from the memory 220 of the server module200 (Step S208) and retrieves the transfer list 334 from the memory 330of the storage module 300 (Step S209).

Specifically, the DMA controller 232 in the data transfer unit 231acquires the first address from the server module 200 and acquires thesecond address from the storage module 300. Alternatively, the DMAcontroller 232 may acquire the transfer lists 224 and 334 themselves.The DMA controller 232 temporarily holds the acquired addresses or thetransfer lists 224 and 334.

The transfer module 230 refers to the transfer list 224 held in thememory 220 of the server module 200 to retrieve the data copied to thememory 220 (Step S210).

Specifically, the DMA controller 232 in the data transfer unit 231refers to the transfer list 224 held in the memory 220 of the servermodule 200 with the first address to retrieve the data copied to thememory 220. The DMA controller 232 is to retrieve data on apredetermined data size basis. For example, the DMA controller 232retrieves data in blocks of 512 bytes.

Next, the transfer module 230 writes the retrieved data to the memory330 of the storage module 300 (Step S211). Specifically, the followingprocessing is performed.

The data checker 233 in the data transfer unit 231 converts theretrieved data into the data format for the storage module 300. Forexample, the data checker 233 attaches a data assurance code to theretrieved data. Through this operation, the data is converted into520-byte data to be handled by the storage module 300.

The data transfer unit 231 refers to the transfer list 224 held in thememory 220 of the server module 200 with the first address and refers tothe transfer list 334 held in the memory 330 of the storage module 300with the second address.

The data transfer unit 231 determines the storage area of the memory 330to write the converted data based on the transfer lists 224 and 334.Furthermore, the DMA controller 232 in the data transfer unit 231 writesthe converted data to the determined storage area in the memory 330.

For example, the data transfer unit 231 adjusts the alignment todetermine the storage area in the memory 330.

The data transfer unit 231 repeats the foregoing processing until allthe data to be written has been written.

Described above is the explanation of the processing of Step S211.

Next, after writing all the data to be written to the memory 330, thetransfer module 230 sends a notice of completion of DMA transfer to thestorage controller 331 (Step S212).

Upon receipt of the notice of completion of DMA transfer, the storagecontroller 331 sends a notice of completion (storage command) for the OS221 (Step S213).

Upon receipt of the notice of completion (storage command), the transfermodule 230 converts the notice of completion (storage command) from thestorage command to a server command and sends the converted notice ofcompletion (server command) to the OS 221 (Step S214). Since theconversion of the command is similar to Step S204, the explanation isomitted.

In the case where the transfer lists 224 and 334 themselves areretrieved at Steps S208 and S209, the transfer module 230 refers to thetransfer lists 224 and 334 to create a conversion list to adjust thealignment for data storage. In this case, the data transfer unit 231determines the storage area of the memory 330 to write the converteddata based on the conversion list at Step S211. The DMA controller 232then writes the converted data to the determined storage area in thememory 330.

For example, the conversion list could be a list which associates theaddresses in the transfer list 224 with the addresses in the transferlist 334.

The creation of the conversion list needs to take the above describedalignment into account. This is because the data unit size handled bythe server module 200 is different from the data unit size handled bythe storage module 300. Further, other causes are the effects from theaddition of the assurance codes by the data checker 233, the virtualstorage management by the OS 221 running in the server module 200 andthe memory management by the storage controller 331 running in thestorage module 300.

For example, when writing 8192 bytes data from the server module 300,assurance codes are attached to the data and the data area is 8320 bytesin the storage module 300. The DMA transfer on the PCIe bus transfersdata in power-of-two bytes blocks. Thus, the conversion list is createdso as to carry out transfers two times for 8192 bytes data and 128 bytesdata.

On the other hand, when the transfer list in the server module 200designates noncontiguous two 4096 bytes areas for writing 8192 bytes,the conversion list is created so as to carry out transfers four timesfor 4096 bytes data, 64 bytes data, 4096 bytes data, 64 bytes data.

Referring to FIG. 10, an example case will be described in which thetransfer module 230 controls transfer of 8192 bytes data to be writtenfor a write request from the memory 220 of the server module 200 to thememory 330 of the storage module 300.

The transfer module 230 acquires the transfer list 224 from the servermodule 200. As described above, the transfer list 224 indicates thestart address and the data length of each of areas prepared on thememory 220 by the server module 200 and storing data to be written for awrite request. The transfer list 224 in FIG. 10 indicates that the 8192bytes write data are divided and stored in the 4096 bytes area startingfrom the address A and the 4096 bytes area starting from the address B.The transfer module 230 acquires the transfer list 334 from the storagemodule 300. The transfer list 334 indicates the start address and theaddress length of each of areas prepared on the memory 330 of thestorage module 300 for storing temporarily data to be written for awrite request. The transfer list 334 in FIG. 10 indicates that the 8192bytes write data for the write request and the assurance codes arestored in the 8320 bytes area starting from the address A′.

The transfer module 230 creates a conversion list based on the transferlist 224 and the transfer list 334. Specifically, the transfer module230 identifies the address of the areas to store the assurance codesfrom the transfer list 334. The transfer module 230 associates theaddresses of areas excluding the areas to store the assurance codes(namely, areas to store the read data for the read request on the memory330) as the data transfer destination addresses with the addresses onthe memory 220 of the server module 200 designated for storingtemporarily the write data in the transfer list 224 as the data transfersource addresses. The conversion list in FIG. 10 associates the addressof the 4096 bytes area starting from the address A′ on the memory 330 asthe data transfer destination address with the 4096 bytes area startingfrom the address A on the memory 220 as the data transfer sourceaddress. Further, the conversion list in FIG. 10 associates the addressof the 4096 bytes area starting from the address A′+4160 bytes on thememory 330 as the data transfer destination address with the 4096 bytesarea starting from the address B on the memory 220 as the data transfersource address.

The transfer module 230 controls the transfer of the data to be writtenfor the write request from the memory 220 of the server module 200 tothe memory 330 of the storage module 300 based on the created conversionlist.

As described above, the conversion list allows the transfer module 230to manage integrally the memory 220 and the memory 330. Therefore, thetransfer module 230 is capable of controlling directly the data transferbetween the memory 220 and the memory 330 without other processors. Asthe transfer module 230 controls directly the data transfer between thememory 220 and the memory 330 in this example, the overhead is inhibitedand the high-speed data transfer between the memory 220 and the memory330 is achieved in comparison with data transfer through pluralprocessors (for example, the processor 320 of the storage module 300 andthe processor 220 of the server module 200) or buffer memories of theprocessors in the data transfer.

It should be noted that the transfer module 230 is included in theserver module 200 in Embodiment 1; however, this invention is notlimited to this. For example, the transfer module 230 may be mounted onthe backplane 400. That is to say, the transfer module 230 is notlimited to its mounting location but is sufficient if the I/O bus of theserver module 200 can be connected to the I/O bus of the storage module300.

In Embodiment 1, two disk controllers 310 achieve redundancy of thestorage controller 331 but this invention is not limited to this. Forexample, a single disk controller 310 may be logically divided toimplement two storage controllers 331. In such a case, two I/Fs 360 areconnected to the single disk controller.

As described above, in Embodiment 1, the transfer module 230 performsdata transfer between the memory 220 of the server module 200 and thememory 330 of the storage module 300.

In data transfer in an existing computer system, protocol conversion isperformed at the end point of the server module 200 and the end point ofthe storage module 300. In an example of traditional reading, the HBA240 of the server module 200 converts the protocol in transferring aread request to the storage module 300 and the TBA 350 of the storagemodule 300 converts the protocol in transferring retrieved data.

In this invention, however, the server module 200 and the storage module300 send commands whose protocols are not converted to the transfermodule 230 and the transfer module 230 converts the protocols.

Specifically, the server module 200 sends server commands to thetransfer module 230 as they are and the transfer module 230 converts thereceived server commands into storage commands to send the convertedcommands to the storage module 300. The storage module 300 sends storagecommands to the transfer module 230 as they are; the transfer module 230converts the received storage commands into server commands to send theconverted commands to the server module 200.

Consequently, this invention has an effect of reducing the overhead indata transfer caused by protocol conversion.

Furthermore, since the transfer module 230 directly accesses the memory220 of the server module 200 and the memory 330 of the storage module300, this invention attains high-speed data transfer between memoriesvia neither the processor 310 of the server module 200 nor the processor320 of the storage module 300.

In Embodiment 1, the transfer module 230 is mounted in the server module200 to achieve data transfer with high performance. That is to say, itis unnecessary to change the software configuration of the server module200 or the hardware and software configuration of the storage module300. Accordingly, the computer system in Embodiment 1 can be created atlow cost.

The reason why the transfer module 230 in Embodiment 1 is mounted in theserver module 200 is that, if the transfer module 230 is mounted in thestorage module 300, every server module 200 needs a transfer module 230.In other words, the storage module 300 might be physically difficult tomount transfer modules 230 as many as the maximum number of connectableserver modules 200.

Embodiment 2

Embodiment 1 provided a server apparatus 100 including server modules200 and a storage module 300 within the same chassis; Embodiment 2 isdifferent from Embodiment 1 in the point that the server modules 200 andthe storage module 300 are in independent chassis. Hereinafter,Embodiment 2 is described mainly in differences from Embodiment 1.

FIG. 7 is a block diagram illustrating a configuration example of acomputer system in Embodiment 2 of this invention.

The computer system in Embodiment 2 is composed of a plurality of servermodules 200 and a plurality of storage modules 300.

The hardware configuration and software configuration of the servermodule 200 and the storage module 300 are the same as those inEmbodiment 1; accordingly, the explanation is omitted.

The server module 200-1 and the storage module 300-1 in Embodiment 2 aredifferent from Embodiment 1 in the point that they are directlyconnected via connection lined such as metal cabled. Two connectionlines are connected to the I/F 260 of the server module 200 and theother ends of the connection lines are connected to different I/Fs 360of the storage module 300. Since the other connections are the same asthose in Embodiment 1, the explanation is omitted.

The processing of the transfer module 230 in Embodiment 2 is the same asthat shown in FIGS. 5 and 6 in Embodiment 1; accordingly, theexplanation is omitted.

According to Embodiment 2, high-speed data transfer can be attained eventhough the server module 200 and the storage module 300 are in differentchassis.

Embodiment 3

Embodiment 3 differs from Embodiment 1 in the points that the servermodules 200 and the storage module 300 are in independent chassis andthat each of them has a transfer module. Embodiment 3 is based on theassumption that the storage module 300 can mount transfer modules asmany as the storage module 300 needs.

In the case where only the server module 200 has a transfer module 230,the storage module 300 manages the I/O bus from the disk controllers 310to the transfer module 230 as the I/O connection area of the storagemodule 300.

For this reason, if a fault occurs in a connection line between a servermodule 200 and the storage module 300, the entire storage module 300might go down because the storage module 300 recognizes the fault as afault in the I/O connection area. Accordingly, the redundancy in thestorage module 300 cannot function appropriately.

In view of the above, the storage module 300 in Embodiment 3 includestransfer modules 380. In this case, the storage module 300 manages theI/O bus from the disk controllers 310 to the transfer modules 380 of thestorage module 300 for its own I/O connection area.

Hereinafter, Embodiment 3 is described mainly in differences fromEmbodiment 1.

FIG. 8 is a block diagram illustrating a configuration example of acomputer system in Embodiment 3 of this invention.

The computer system in Embodiment 3 is composed of a plurality of servermodules 200 and a plurality of storage modules 300.

The hardware configuration and the software configuration of each servermodule 200 in Embodiment 3 is the same as those in Embodiment 1; theexplanation is omitted.

Each storage module 300 in Embodiment 3 includes transfer modules 380-1and 380-2. The transfer module 380-1 is connected to the disk controller310-1 and the transfer module 380-2 is connected to the disk controller310-2. The software configuration of the storage module 300 inEmbodiment 3 is the same as that in Embodiment 1; the explanation isomitted.

The configuration of the transfer modules 380-1 and 380-2 is the same asthat of the transfer module 230; the explanation is omitted.

In Embodiment 3, the transfer module 230 in the server module 200functions as a bridge. That is to say, in the transfer module 230, datais transferred between connection ports 236 via the bridge 235 not viathe data transfer unit 231. Accordingly, the server module 200 may havea common bridge instead of the transfer module 230.

In Embodiment 3, the transfer modules 380-1 and 380-1 of the storagemodule 300 perform the data transfer illustrated in FIGS. 5 and 6. Thetransfer modules 380-1 and 380-2 independently perform data transfer.

When a fault occurs in a connection line connecting a server module 200and the storage module 300, the transfer module 380 changes the mode ofthe disk controller 310 connected from the transfer module 380 into astandby mode. This operation minimizes the range affected by the faultin the connection line.

For example, in the case of a fault in the connection line connectingthe server module 200-1 and the disk controller 310-1, the transfermodule 380-1 changes the disk controller 310-1 into a standby mode.Meanwhile, the transfer module 380-2 takes over the data transfer.Consequently, even if a fault occurs in a connection line connecting aserver module 200 and the storage module 300, the other server modules200 can be prevented from being affected by this fault.

In the case of a fault in the I/O bus in a server module 200, thefollowing processing is performed. The root complex in the chipset(not-shown) of the server module 200 performs degeneration such asseparating the failed I/O bus. The same processing is performed in thecase of a fault in the I/O bus in a storage module 300.

To configure the transfer module 230 in the server module 200 as abridge, the following method can be taken.

When the server module 200 is connected to the storage module 300 with aconnection line, the OS 221 of the server module 200 inquires thestorage module 300 whether the storage module 300 has a transfer module380. If the OS 221 receives a response indicating that the storagemodule 300 has a transfer module 380, it configures its own transfermodule 230 as a bridge.

Alternatively, the system administrator or a user may initiallyconfigure the transfer module 230 of the server module 200 as a bridge.

In the example shown in FIG. 8, the transfer modules 380 are connectedto different I/Fs 360, but this invention is not limited to this.

The number of transfer modules 380 may be one. In such a case, thesingle transfer module 380 is connected to the I/Fs 360-1 and 360-2 viadifferent I/O buses. The transfer module 380 logically divides thefunctional units to perform I/O processing in parallel.

Embodiment 3 can increase the fault tolerance and achieve high-speeddata transfer. It should be noted that Embodiment 1 can have the sameconfiguration as Embodiment 3. That is to say, the storage module 300-1may have a transfer module 380.

This invention is not limited to the above-described embodiments butincludes various modifications. The above-described embodiments areexplained in details for better understanding of this invention and arenot limited to those including all the configurations described above. Apart of the configuration of one embodiment may be replaced with that ofanother embodiment; the configuration of one embodiment may beincorporated to the configuration of another embodiment. A part of theconfiguration of each embodiment may be added, deleted, or replaced bythat of a different configuration.

The above-described configurations, functions, and processors, for allor a part of them, may be implemented by hardware: for example, bydesigning an integrated circuit. The above-described configurations andfunctions may be implemented by software, which means that a processorinterprets and executes programs providing the functions. Theinformation of programs, tables, and files to implement the functionsmay be stored in a storage device such as a memory, a hard disk drive,or an SSD (Solid State Drive), or a storage medium such as an IC card,or an SD card.

Representative aspects of the present invention in addition to theaspects described in the claims are as follows:

1. A computer system comprising:

a server module;

a storage module; and

a transfer module,

the server module including a first processor, a first memory, a firstinterface for connecting the server module to other apparatuses, and afirst connection line connecting the first processor, the first memory,and the first interface,

the storage module including a controller including a second processorand a second memory, a storage device, a second interface for connectingthe storage module to other apparatuses, and a second connection lineconnecting the controller, the storage device, and the second interface,

the transfer module being connected to the first connection line and thesecond connection line,

wherein the server module is configured to:

create a first transfer list including an address and an address lengthto be used in storing data to be transferred to the first memory orretrieving the data to be transferred from the first memory; and

send an I/O request for an I/O between the first memory and the secondmemory to the transfer module,

wherein the storage module is configured to:

receive the I/O request from the transfer module;

create a second transfer list including an address and an address lengthto be used in storing the data to be transferred to the second memory orretrieving the data to be transferred from the second memory; and

send a data transfer request to the transfer module,

wherein the transfer module is configured to:

acquire, upon receipt of the data transfer request from the storagemodule, the data to be transferred from the first memory or the secondmemory with reference to the first transfer list and the second transferlist; and

transfer the acquired data to be transferred to the first memory or thesecond memory with reference to the first transfer list and the secondtransfer list.

2. A computer system according to the aspect 1,

wherein the transfer module is configured to:

in a case where the transfer module receives a first I/O request toretrieve data from the second memory to the first memory,

convert a command corresponding to the first I/O request into a commandto be used in the storage module to send the converted command to thestorage module;

acquire the data to be retrieved with reference to the second transferlist to convert the acquired data into data in a format to be handled bythe server module by removing a data assurance code attached to theacquired data for checking integrity of the data;

determine a storage area in the first memory to write the converted datato be retrieved with reference to the first transfer list and the secondtransfer list, and write the converted data to be retrieved to thedetermined storage area in the first memory; and

notify the storage module of completion of data transfer, and

wherein the transfer module is configured to:

in a case where the transfer module receives a second I/O request towrite data in the first memory to the second memory,

convert a command corresponding to the second I/O request into a commandto be used in the storage module to send the converted command to thestorage module;

acquire the data to be written with reference to the first transfer listto convert the acquired data into data in a format to be handled by thestorage module by attaching a data assurance code;

determine a storage area in the second memory to write the converteddata to be written with reference to the first transfer list and thesecond transfer list, and write the converted data to be written to thedetermined storage area in the second memory; and

notify the storage module of completion of data transfer.

3. A server module connected with a storage module including acontroller including a first processor and a first memory, a storagedevice, a first interface for connecting the storage module to otherapparatuses, and a first connection line connecting the controller, thestorage device, and the first interface, the server module comprising:

a second processor;

a second memory;

a second interface for connecting the server module to otherapparatuses;

a second connection line connecting the second processor, the secondmemory, and the second interface; and

a transfer module connected to the first connection line and the secondconnection line,

wherein the transfer module is configured to:

retrieve, upon receipt of an I/O request for an I/O between the firstmemory and the second memory from the second processor, a first transferlist from the first memory, the first transfer list being created by thefirst processor and including an address and an address length to beused in storing data to be transferred to the first memory or retrievingthe data to be transferred from the first memory;

retrieve a second transfer list from the second memory, the secondtransfer list being created by the second processor and including anaddress and an address length to be used in storing data to betransferred to the second memory or retrieving the data to betransferred from the second memory;

acquire the data to be transferred from the first memory or the secondmemory with reference to the first transfer list and the second transferlist; and

transfer the acquired data to be transferred to the first memory or thesecond memory with reference to the first transfer list and the secondtransfer list.

4. A server module according to the aspect 3,

wherein the transfer module is configured to:

in a case where the transfer module receives a first I/O request toretrieve data from the first memory to the second memory,

convert a command corresponding to the first I/O request into a commandto be used in the storage module to send the converted command to thestorage module;

acquire the data to be retrieved with reference to the first transferlist to convert the acquired data into data in a format to be handled bythe server module by removing a data assurance code attached to theacquired data for checking integrity of the data;

determine a storage area in the second memory to write the converteddata to be retrieved with reference to the first transfer list and thesecond transfer list and write the converted data to be retrieved to thedetermined storage area in the second memory; and

notify the storage module of completion of data transfer, and

wherein the transfer module is configured to:

in a case where the transfer module receives a second I/O request towrite data in the second memory to the first memory,

convert a command corresponding to the second I/O request into a commandto be used in the storage module to send the converted command to thestorage module;

acquire the data to be written with reference to the second transferlist to convert the acquired data into data in a format to be handled bythe storage module by attaching a data assurance code;

determine a storage area in the first memory to write the converted datato be written with reference to the first transfer list and the secondtransfer list, and write the converted data to be written to thedetermined storage area in the first memory; and

notify the storage module of completion of data transfer.

5. A storage module connected with a server module including a firstprocessor, a first memory, a first interface for connecting the servermodule to other apparatuses, and a first connection line connecting thefirst processor, the first memory, and the first interface, the storagemodule comprising:

a controller including a second processor and a second memory;

a storage device;

a second interface for connecting the storage module to otherapparatuses;

a second connection line connecting the controller, the storage device,and the second interface; and

a transfer module connected to the first connection line and the secondconnection line,

wherein the transfer module is configured to:

retrieve, upon receipt of an I/O request for an I/O between the firstmemory and the second memory from the first processor, a first transferlist from the first memory, the first transfer list being created by thefirst processor and including an address and an address length to beused in storing data to be transferred to the first memory or retrievingthe data to be transferred from the first memory;

retrieve a second transfer list from the second memory, the secondtransfer list being created by the second processor and including anaddress and an address length to be used in storing data to betransferred to the second memory or retrieving the data to betransferred from the second memory;

acquire the data to be transferred from the first memory or the secondmemory with reference to the first transfer list and the second transferlist; and

transfer the acquired data to be transferred to the first memory or thesecond memory with reference to the first transfer list and the secondtransfer list.

6. A storage module according to the aspect 5,

wherein the transfer module is configured to:

in a case where the transfer module receives a first I/O request toretrieve data from the second memory to the first memory,

convert a command corresponding to the first I/O request into a commandto be used in the storage module to send the converted command to thecontroller;

acquire the data to be retrieved with reference to the second transferlist to convert the acquired data into data in a format to be handled bythe server module by removing a data assurance code attached to theacquired data for checking integrity of the data;

determine a storage area in the first memory to write the converted datato be retrieved with reference to the first transfer list and the secondtransfer list, and write the converted data to be retrieved to thedetermined storage area in the first memory; and

notify the controller of completion of data transfer, and

wherein the transfer module is configured to:

in a case where the transfer module receives a second I/O request towrite data in the first memory to the second memory,

convert a command corresponding to the second I/O request into a commandto be used in the storage module to send the converted command to thecontroller;

acquire the data to be written with reference to the first transfer listto convert the acquired data into data in a format to be handled by thestorage module by attaching a data assurance code;

determine a storage area in the second memory to write the converteddata to be written with reference to the first transfer list and thesecond transfer list, and write the converted data to be written to thedetermined storage area in the second memory; and

notify the controller of completion of data transfer.

What is claimed is:
 1. A computer system comprising: a server moduleincluding a first processor and first memory; a storage module includinga second processor, a second memory and a storage device; and whereinthe server module further includes a transfer module which controls adata transfer between the first memory of the server module and thesecond memory of the storage module, wherein when the first processor ofthe server module issues a read command to the second processor of thestorage module via the transfer module, wherein the transfer moduleretrieves a first transfer list including a first address of the firstmemory for the read command, which is set by the first processor;wherein the transfer module further retrieves a second transfer listincluding a second address of the second memory, in which datacorresponding to the read command read from the storage device is storedtemporarily by the second processor, wherein the transfer module createsa conversion list by associating the first address as the data transferdestination address with the second address as the data transfer sourceaddress in accordance with the first transfer list and the secondtransfer list, wherein the transfer module executes a data transfer fromthe second memory to the first memory based on the conversion list,wherein the transfer module sends a notice of a completion of the datatransfer to the second processor, and wherein the transfer module tosends a notice of a completion of the read command to the firstprocessor in response to receiving an instruction from the secondprocessor.
 2. A computer system according to claim 1, wherein a dataformat handled by the server module is different form a data formathandled by the storage module, wherein, in a case where the transfermodule sends data in the second address of the second memory in thestorage module to the first address of the first memory in the servermodule, the transfer module converts the data into data in the formathandled by the server module by removing a data assurance code attachedto the data for checking integrity of the data, and wherein, in a casewhere the transfer module receives the read command to retrieve datafrom the second memory to the first memory, the transfer module convertsa command corresponding to the read command into a command to be used inthe storage module to send the converted command to the storage module.3. A computer system according to claim 1, further comprising a backplain located between the transfer module and the storage module.
 4. Acomputer system according to claim 1, wherein the server module includesthe transfer module.
 5. A computer system according to claim 1, whereinthe sever module, the storage module and the transfer module communicatewith each other based on PCIe protocol.
 6. A computer system comprising:a server module including a first processor and a first memory; astorage module including a second processor, a second memory and astorage device; and wherein the server module further includes atransfer module which controls a data transfer between the first memoryof the server module and the second memory of the storage module,wherein when the first processor of the server module issues a writecommand to the second processor of the storage module via the transfermodule, wherein the transfer module retrieves a first transfer listincluding a first address of the first memory for the write command,which is set by the first processor, wherein the transfer module furtherretrieves a second transfer list including a second address of thesecond memory, in which data corresponding to the write command isstored temporarily by the second processor, wherein the transfer modulecreates a conversion list by associating the second address as the datatransfer destination with the first address as the data transfer sourceaddress in accordance with the first transfer list and the secondtransfer list, wherein the transfer module executes a data transfer fromthe first storage memory to the second memory based on the conversionlist, the transfer module sends a notice of a completion of the datatransfer to the second processor, and the transfer module sends a noticeof a completion of the write command to the first processor in responseto receiving an instruction from the second processor.
 7. A computersystem according to claim 6, wherein a data format handled by the servermodule is different form a data format handled by the storage module,wherein, in a case where the transfer module sends data in the firstaddress of the first memory in the server module to the second addressof the second memory in the storage module, the transfer module convertsthe data into data in the format handled by the storage module by addinga data assurance code attached to the data for checking integrity of thedata, and wherein, in a case where the transfer module receives thewrite command to send data from the first memory to the second memory,the transfer module converts a command corresponding to the writecommand into a command to be used in the storage module to send theconverted command to the storage module.
 8. A computer system accordingto claim 6, further comprising a back plain located between the transfermodule and the storage module.
 9. A computer system according to claim6, wherein the server module includes the transfer module.
 10. Acomputer system according to claim 6, wherein the sever module, thestorage module and the transfer module communicate each other base onPCIe protocol.
 11. A computer system comprising: a server moduleincluding a first processor and first memory; a storage module includinga second processor, a second memory and a storage device, wherein theserver module further includes a transfer module which controls a datatransfer between the first memory of the server module and the secondmemory of the storage module, wherein when the first processor of theserver module issues a read command to the second processor of thestorage module via the transfer module, wherein the transfer moduleretrieves a first transfer list including a first address of the firstmemory for the read command, which is set by the first processor,wherein the transfer module further retrieves a second transfer listincluding a second address of the second memory, in which datacorresponding to the read command read from the storage device is storedtemporarily by the second processor, wherein the transfer module createsa conversion list which corresponds the second address of the secondmemory to the first address of the first memory regarding a differencebetween a size of data format handled by the server module and a size ofdata format handled by the storage module, wherein the transfer moduleexecutes a data transfer from the second memory to the first memorybased on the conversion list; wherein the transfer module sends a noticeof a completion of the data transfer to the second processor, andwherein the transfer module sends a notice of the completion of the readcommand to the first processor in response to receiving an instructionfrom the second processor.
 12. A computer system comprising: a servermodule including a first processor and a first memory; a storage moduleincluding a second processor, a second memory and a storage device; andwherein the server module further includes a transfer module whichcontrols a data transfer between the first memory of the server moduleand the second memory of the storage module wherein when the firstprocessor of the server module issues a write command to the secondprocessor of the storage module via the transfer module, wherein thetransfer module retrieves a first transfer list including a firstaddress of the first memory for the write command, which is set by thefirst processor, wherein the transfer module further retrieves a secondtransfer list including a second address of the second memory, in whichdata corresponding to the write command is stored temporarily by thesecond processor, wherein the transfer module creates a conversion listwhich corresponds the first address of the first memory to the secondaddress of the second memory regarding a difference between a size ofdata format handled by the server module and a size of data formathandled by the storage module, wherein the transfer module executes adata transfer from the first memory to the second memory based on theconversion list, wherein the transfer module sends a notice of acompletion of the data transfer to the second processor, and wherein thetransfer module sends a notice of the completion of the write command tothe first processor in response to receiving an instruction from thesecond processor.